Interpret naive datetimes as UTC #686
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gadomski
force-pushed
the
issues/644-naive-datetime
branch
from
57a5a26 to
76b9629
Compare
gadomski
force-pushed
the
issues/644-naive-datetime
branch
from
76b9629 to
7f57f80
Compare
TomAugspurger
approved these changes
May 14, 2024
Good point — I hadn't thought about that. Do you think it's enough of a change to warrant a "MAJOR" release (i.e. v0.8.0) to get people's attention? |
|
Maybe. I'm a fan of @jacobtomlinson's effver. Getting users to pause and think about whether they're using naive datetime objects seems worthwhile. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue(s):
PR Checklist: